Repository navigation
feat(relay): record per-leg frame progress for stall triage - #197
Merged
Merged
Conversation
abruption
force-pushed
the
feat/172-receiver-attempt-correlation
branch
from
September 24, 2026 12:22
eda30be to
68eb689
Compare
abruption
force-pushed
the
feat/161-relay-frame-monitoring
branch
from
September 24, 2026 12:25
896ca7b to
19315f8
Compare
abruption
changed the base branch from
feat/172-receiver-attempt-correlation
to
main
September 24, 2026 12:25
abruption
force-pushed
the
feat/161-relay-frame-monitoring
branch
from
September 24, 2026 12:26
19315f8 to
053d07c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #161. Built on merged #196 for per-attempt correlation. This is monitoring-only; the underlying #161 root cause remains unknown.
Monitoring change
This supports investigation if the public-path stall recurs. A completed socket send is not proof of peer delivery, and these counters cannot determine whether Cloudflare, OCI, or a transit hop is at fault. No production service, security setting, or existing unmerged #161 observability worktree was changed.
Verification
Existing sqlite ResourceWarning in test_control_backup_snapshot.py remains unrelated.